Skip to content

fix: resolve JavaScript lint errors (no-error-string-concat, no-new-array)#10566

Closed
sputnik-mac wants to merge 2 commits intostdlib-js:developfrom
sputnik-mac:fix/lint-errors
Closed

fix: resolve JavaScript lint errors (no-error-string-concat, no-new-array)#10566
sputnik-mac wants to merge 2 commits intostdlib-js:developfrom
sputnik-mac:fix/lint-errors

Conversation

@sputnik-mac
Copy link
Copy Markdown

Description

Fixes two JavaScript lint errors caught in the automated lint workflow (issue #10556).

Changes

1. lib/node_modules/@stdlib/utils/async/for-each-right/examples/index.js

  • Replaced string concatenation in error message with @stdlib/string/format
  • Fixes: stdlib/no-error-string-concat lint error at line 45

2. lib/node_modules/@stdlib/math/strided/special/ahavercos-by/test/test.ndarray.js

  • Replaced new Array( 5 ) constructor calls with Array.from( { 'length': 5 } )
  • Fixes: stdlib/no-new-array lint errors at lines 76 and 84

Checklist

Closes #10556

… error message

Use `@stdlib/string/format` instead of string concatenation in the error
message to comply with the `stdlib/no-error-string-concat` lint rule.

Signed-off-by: Sputnik-MAC <sputnik.mac.001@gmail.com>
…y.from()

Replace `new Array( 5 )` constructor calls with `Array.from( { 'length': 5 } )`
to comply with the `stdlib/no-new-array` lint rule.

Signed-off-by: Sputnik-MAC <sputnik.mac.001@gmail.com>
@stdlib-bot stdlib-bot added the First-time Contributor A pull request from a contributor who has never previously committed to the project repository. label Feb 28, 2026
@stdlib-bot
Copy link
Copy Markdown
Contributor

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

  1. Please read our contributing guidelines.

  2. Update your pull request description to include this checked box:

    - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

  • The developer's certificate of origin
  • Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

@stdlib-bot stdlib-bot added the Needs Review A pull request which needs code review. label Feb 28, 2026
@stdlib-bot
Copy link
Copy Markdown
Contributor

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

Next Steps

  1. A project maintainer will approve GitHub Actions workflows for your PR.
  2. All CI checks must pass before your submission can be fully reviewed.
  3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

@stdlib-bot stdlib-bot added the Good First PR A pull request resolving a Good First Issue. label Feb 28, 2026
@kgryte
Copy link
Copy Markdown
Member

kgryte commented Feb 28, 2026

Ref: #10557

@kgryte kgryte added autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. and removed Needs Review A pull request which needs code review. labels Feb 28, 2026
@stdlib-bot
Copy link
Copy Markdown
Contributor

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.

@stdlib-bot stdlib-bot closed this Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autoclose: Already Resolved Pull request which should be auto-closed due proposed changes duplicating already included changes. First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Good First PR A pull request resolving a Good First Issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix JavaScript lint errors

3 participants